Updating dynamic data usage plans and statistics

ABSTRACT

Embodiments enable data usage plans and data usage statistics to be shared among user computing devices. In some embodiments, a web service receives a schema populated with data describing the data usage plan from a mobile operator. The web service distributes the populated schema to the user computing devices, and subsequently distributes updated portions of the schema as the data usage plan is updated by the mobile operator. The web service may also collect the data usage statistics from the user computing devices and the mobile operator, reconcile any differences, and send synchronization notifications to the user computing devices based on the reconciliation. In some embodiments, users are able to view bandwidth consumption by a plurality of user computing devices sharing the same data usage plan.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of pending U.S. ProvisionalApplication No. 61/696,472, filed Sep. 4, 2012, pending U.S. ProvisionalApplication No. 61/591,503, filed Jan. 27, 2012, and pending U.S.Provisional Application No. 61/591,509, filed Jan. 27, 2012. Theentirety of these provisional applications is hereby incorporated byreference herein.

This application is related to the following applications: U.S. patentapplication entitled “Tracking Data Usage Under a Schematized Data UsagePlan,” U.S. patent application entitled “Managing Data Transfers OverNetwork Connections Based on Priority and a Data Usage Plan,” U.S.patent application entitled “On-Device Attribution of Network DataUsage,” U.S. patent application entitled “Predicting Network DataConsumption Relative to Data Usage Patterns,” U.S. patent applicationentitled “Data Usage Profiles for Users and Applications,” U.S. patentapplication entitled “Recommendations for Reducing Data ConsumptionBased on Data Usage Profiles,” U.S. patent application entitled“Dynamically Adjusting a Data Usage Plan Based on Data UsageStatistics,” and U.S. patent application entitled “Managing Network DataTransfers in View of Multiple Data Usage Plans.” All of theseapplications are incorporated by reference herein in their entirety.

BACKGROUND

With the increased popularity of smart telephones, tablets, and othermobile devices, there has been a similar increase in the amount of datahandled by the networks of mobile operators. To reduce the strain onnetwork infrastructure and to reduce network transfer costs, mobileoperators are shifting from offering simple unlimited mobile data plansto offering capped and metered plans. Some of these capped and meteredplans are complex, with allotted data caps varying based on networktype, time of day, etc. Further, the fees for exceeding the allotteddata caps may be significant and may also vary based on network type,time of day, etc. The existing systems generally lack mechanisms to helpthe user understand and manage data consumption in view of the datausage plans.

As a result, with the existing systems, users can unknowingly exceed theallotted data caps and experience bandwidth throttling (e.g., areduction or limit placed upon the rate of consumption) and/or bepresented with a much larger than normal monthly bill, resulting in“bill shock.” Throttling and bill shock can impact the user experience,leading to dissatisfied customers, increased customer service calls, andnegative impressions of the mobile operators.

SUMMARY

Embodiments of the disclosure enable the collection and synchronizationof data describing data usage plans and data usage statistics. A schemapopulated with data describing at least one data usage plan is receivedfrom at least one mobile operator. The data usage plan is associatedwith one or more user computing devices. The received, populated schemais distributed to the user computing devices. An updated portion of theschema is subsequently received from the mobile operator. The updatedportion of the schema corresponds to an updated portion of the datausage plan. Only the received, updated portion of the schema isdistributed to the user computing devices.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an exemplary block diagram illustrating a web serviceinteracting with a mobile operator and user computing devices.

FIG. 2 is an exemplary flow chart illustrating operation of a webservice to obtain and distribute data describing a data usage plan, or aportion thereof.

FIG. 3 is an exemplary flow chart illustrating operation of a computingdevice to collect and reconcile data usage statistics describing dataconsumed under a data usage plan.

FIG. 4 is an exemplary user interface illustrating configuration optionsfor importing data describing a data usage plan.

FIG. 5 is an exemplary user interface illustrating synchronization ofdata describing a data usage plan.

FIG. 6 is an exemplary user interface illustrating a summary of networkdata usage with different types of network connections.

FIG. 7A is an exemplary user interface illustrating data usage by amobile computing device consuming network data under a data usage planwith a monthly limit.

FIG. 7B is an exemplary user interface illustrating data usage by amobile computing device consuming network data under a pay-as-you-godata usage plan.

FIG. 7C is an exemplary user interface illustrating data usage by amobile computing device consuming network data under a data usage planwith unlimited data usage.

FIG. 8 is an exemplary block diagram illustrates a mobile computingdevice having a tile for displaying network data usage statistics to auser.

Corresponding reference characters indicate corresponding partsthroughout the drawings.

DETAILED DESCRIPTION

Referring to the figures, embodiments of the disclosure enable acentralized web service 108 to interact with user computing devices andmobile operators 111 to distribute data usage plans and to aggregatedata usage statistics. For example, the web service 108 pullsinformation from the mobile operators 111 regarding customers (e.g.,users 104) and pushes data usage plan changes or updates to a given user104, segments of the users 104, or each of the users 104.

In some embodiments, the web service 108 receives a schema 116 populatedwith data relating to a data usage plan from the mobile operator 111 anddistributes the populated schema 116 to one or more of the usercomputing devices. The data usage plan represents the terms andconditions (e.g., data consumption allotment) under which the mobileoperator 111 provides data transfer services to the user computingdevices. As the mobile operator 111 updates portions of the data usageplan, the web service 108 may receive and synchronize only the updatedportions of the schema 116 with the user computing devices, in someembodiments. For example, the web service 108 does not distribute theother portions of the schema 116 that were not updated.

The web service 108 may further generate, monitor, collect, and/orreceive the data usage statistics from the mobile operators 111 and fromone or more of the user computing devices. The data usage statisticsrepresent an amount of data consumed by the user computing devices underthe data usage plan. The web service 108 reconciles any differences inthe received data usage statistics, and sends a synchronizationnotification to the user computing devices based on the reconciliation.

Referring to FIG. 1, an exemplary block diagram illustrates the webservice 108 interacting with the mobile operator 111 and user computingdevices. The user computing devices include, for example, a mobilecomputing device 102 and other computing devices 106. The user computingdevices communicate over one or more networks 109. In some embodiments,one or more of the user computing devices are associated with a datausage plan. For example, a plurality of the user computing devices mayshare data consumption allotted under the same or common data usageplan.

The user computing devices include any device executing instructions(e.g., as application programs, operating system functionality, or both)to implement operations and functionality. The user computing devicesmay include, for example, the mobile computing device 102 or any otherportable device. In some embodiments, the mobile computing device 102includes a mobile telephone (e.g., mobile telephone 404 in FIG. 4),laptop, tablet, computing pad, netbook, gaming device, e-reader, and/orportable media player. The other computing devices 106 may include lessportable devices such as desktop personal computers, kiosks, andtabletop devices that have network connectivity capabilities.Additionally, each user computing device may represent a group ofprocessing units. While aspects of the disclosure may be describedherein with reference to the mobile computing device 102, thedescriptions are applicable to any of the user computing devices.

Communication to/from the user computing devices may occur using anyprotocol or mechanism over one or more of the networks 109. The networks109 represent any infrastructure or other means for sending and/orreceiving data. The networks 109 may include wired and/or wirelessnetworks.

One or more of the mobile operators 111 communicate with the web service108 and/or the user computing devices via the network 109. Further, theuser computing devices communicate with the web service 108, or otherentity that performs the operations described herein as being associatedwith the web service 108. The web service 108 may further store, or haveaccess to, a computer-executable schema component 122 and acomputer-executable statistics component 124. Operation of the schemacomponent 122 and the statistics component 124, when executed, isdescribed below with reference to FIG. 2.

For convenience in illustrating and describing FIG. 1, the mobilecomputing device 102 and the other computing devices 106 are associatedwith a common data usage plan of the user 104. For example, the mobilecomputing device 102 may represent the mobile telephone 404 of the user104, while the other computing devices 106 may include a tablet and alaptop associated with the user 104.

In some embodiments, the mobile computing device 102 has at least oneprocessor 110, a memory area 112, and at least one user interface (notshown). The processor 110 includes any quantity of processing units, andis programmed to execute computer-executable instructions forimplementing aspects of the disclosure. The instructions may beperformed by the processor 110 or by multiple processors executingwithin the mobile computing device 102, or performed by a processorexternal to the mobile computing device 102. In some embodiments, theprocessor 110 is programmed to execute instructions such as thoseillustrated in the figures (e.g., FIG. 3).

In some embodiments, the processor 110 represents an implementation ofanalog techniques to perform the operations described herein. Forexample, the operations may be performed by an analog computing deviceand/or a digital computing device.

The mobile computing device 102 further has one or more computerreadable media such as the memory area 112. The memory area 112 includesany quantity of media associated with or accessible by the mobilecomputing device 102. The memory area 112 may be internal to the mobilecomputing device 102 (as shown in FIG. 1), external to the mobilecomputing device 102 (not shown), or both (not shown). In someembodiments, the memory area 112 includes read-only memory and/or memorywired into an analog computing device.

The memory area 112 stores, among other data, one or more applications114. The applications 114, when executed by the processor 110, operateto perform functionality on the mobile computing device 102. Exemplaryapplications 114 include mail application programs, web browsers,calendar application programs, address book application programs,messaging programs, media applications, location-based services, searchprograms, and the like. The applications 114 may communicate withcounterpart applications or services such as the web services 108accessible via the network 109. For example, the applications 114 mayrepresent downloaded client-side applications that correspond toserver-side services executing in a cloud.

The mobile computing device 102 further establishes and maintains one ormore network connections 130 representing communication channels orother means for sending and/or receiving data over the network 109.Exemplary network connections 130 include, but are not limited to,Wi-Fi, cellular, tethered, BLUETOOTH brand communication, near-fieldcommunication (NFC), and more. The network connections 130 may also becategorized into voice, text, data, or other categories or types ofnetwork traffic.

The memory area 112 further stores at least one schema 116. The schema116 represents the data usage plan associated with the user 104 of themobile computing device 102. For example, the user 104 has contractedwith the mobile operator 111 to receive network data transfer servicesfrom the mobile operator 111. The data usage plan describes the servicesprovided by the mobile operator 111, such as the amount of network datathe user 104 can consume during a particular duration (e.g., a billingtime period). For example, the data usage plan describes thresholdvalues 118 associated with the network connections 130 of one or moredevices of the user 104. The threshold values 118 represent the maximumamount of data consumption allotted under the data usage plan for thenetwork connections 130. For example, one threshold value 118 mayindicate the maximum amount of data consumption for a Wi-Fi connection,while another threshold value 118 indicates the maximum amount of dataconsumption for a cellular data connection.

The schema 116 may be defined by the web service 108, by the mobileoperator 111, or by another entity. In general, the schema 116 enablesdescriptions of the parts, components, services, features, or otheraspects of the data usage plan including, but not limited to, multi-ratedata plans, peak times, roaming rates, allotted data consumption pernetwork connection 130, etc. In some embodiments, the schema 116 allowsthe mobile operators 111 to send out updated portions of the schema 116corresponding to updated parts of the data usage plan.

In some embodiments, the schema 116 includes a plurality of fields. Eachof the threshold values 118 may be associated with one or more of thefields. For example, the fields may correspond to one or more of thefollowing: peak times, off-peak times, peak time data consumption quota,off-peak time data consumption quota, peak time data consumptionremaining, off-peak time data consumption remaining, a roaming rate andrules, a mobile operator name, a billing cycle type, a networkconnection type, identification of free hosts available for connection,a list of mobile hotspots, and any other elements or informationpertaining to the data usage plan. The list of free hosts representszero-rated or reduced cost hosts (e.g., visiting particular web sitesdoes not count against the data usage plan).

The schema 116 may also include fields supporting different billingrates per host accessed, per weekend, per night, friends and familyrates, peak and off-peak rates, and more. The schema 116 also allowseach mobile operator 111 the flexibility to define complex plansincluding broadly offered plans, and dynamic, short-term offers tospecific users 104 likely to use a specific part or parts of the overallservices. Other offers based on any combination of the metrics obtainedare available to the mobile operator 111.

The schema 116 stored by the mobile computing device 102 may alsoinclude fields corresponding to data usage statistics collected,generated, or received by the mobile computing device 102 and/or themobile operators 111. For example, to facilitate sharing the data usagestatistics among the mobile operators 111, web service 108, and/or usercomputing devices, the mobile operators 111, web service 108, and theuser computing devices may populate the schema 116 with the data usagestatistics.

While the schema 116 may take any form or structure, the schema 116 maybe implemented as XML schema. Appendix A includes an exemplary XMLschema for use in aspects of the disclosure.

The memory area 112 further stores exemplary computer-executablecomponents such as a communications interface component 126 and a userinterface component 128. In some embodiments, the communicationsinterface component 126 includes a network interface card and/orcomputer-executable instructions (e.g., a driver) for operating thenetwork interface card. In some embodiments, the communicationsinterface is operable with near-field communication (NFC) tags.

The user interface component 128 may include a graphics card fordisplaying data to the user 104 and receiving data from the user 104.The user interface component 128 may also include computer-executableinstructions (e.g., a driver) for operating the graphics card. Further,the user interface component 128 may include a display (e.g., a touchscreen display or natural user interface) and/or computer-executableinstructions (e.g., a driver) for operating the display. The userinterface component 128 may also include one or more of the following toprovide data to the user 104 or receive data from the user 104:speakers, a sound card, a camera, a microphone, a vibration motor, oneor more accelerometers, a BLUETOOTH brand communication module, globalpositioning system (GPS) hardware, and a photoreceptive light sensor.For example, the user 104 may input commands or manipulate data bymoving the computing device in a particular way.

Referring next to FIG. 2, an exemplary flow chart illustrates operationof the web service 108 to obtain and distribute data describing a datausage plan, or a portion thereof. While the operations illustrated inFIG. 2 are performed by the web service 108 in some embodiments, one ormore of the operations may be performed by other devices, including anycomputing device local to, or remote from, the user 104. For example,the operations may be performed by a proxy device in communication withthe web service 108. Alternatively or in addition, the operationsillustrated in FIG. 2 may be performed by an operating system executingon the mobile computing device 102.

At 202, the web service 108 receives, from at least one of the mobileoperators 111, the schema 116 populated with data describing the datausage plan associated with one or more of the user computing devices. At204, the web service 108 distributes the received, populated schema 116to the user computing devices. Subsequently, the web service 108 mayreceive at 206 an updated portion of the schema 116 from the mobileoperator 111. The updated portion of the schema 116 corresponds to anupdated portion of the data usage plan. For example, the mobile operator111 may update one or more of the following: roaming agreements,fallback plans, free hosts, mobile hotspots, and any other element andinformation pertaining to the user's data plan that has an impact ondata usage, cost, and/or tariff.

The web service 108 distributes only the received, updated portion ofthe schema 116 to the user computing devices at 208. In this manner, themobile operator 111 is able to update portions of the data usage planand push only those updated portions (e.g., not the entire data usageplan) to subscribers (e.g., user 104), thus reducing the amount ofnetwork data consumed. In embodiments in which there are multipleupdated portions of the schema 116, the web service 108 may decide todistribute the updated portions in separate batches, such as atdifferent times or during particular time intervals. In this manner, theweb service 108 is able to take advantage of reduced cost networktransfers (e.g., off-peak times) to reduce or at least manage thenetwork data consumption of the user computing devices.

Rather than distributing the populated schema 116 or portions thereof,the web service 108 may send a notification to the user computingdevices to synchronize their version of the populated schema 116 withthat of the web service 108. In such embodiments, upon receipt of thenotification from the web service 108, one or more of the user computingdevices may send a synchronization request to the web service 108. Uponreceipt of the synchronization request, the web service 108 provides thepopulated schema 116 or updated portions of the schema 116 to therequesting user computing devices.

In some embodiments, the web service 108 may store, or have access to,one or more computer-executable components for implementing one or moreof the operations illustrated in FIG. 2. For example, the schemacomponent 122, when executed by the web service 108, receives from themobile operator 111 the schema populated with data describing the datausage plan associated with one or more of the user computing devices.The schema component 122 distributes the received, populated schema tothe user computing device. Subsequently, the web service 108 receives,from the mobile operator 111, an updated portion of the schema 116. Theupdated portion of the schema 116 corresponds to an updated portion ofthe data usage plan (e.g., as updated by the mobile operator 111 such aswhen changing terms of the data usage plan). The schema component 122then distributes only the received, updated portion of the schema 116 tothe user computing device.

In some embodiments, the web service 108 may further collect, reconcile,and distribute data usage statistics to the user computing devices. Thedata usage statistics may be viewed as a current or instant snapshot ofthe amount of data transmitted and/or received (e.g., consumed) by thecomputing devices of the user 104 that share the data usage plan. Theweb service 108 may collect information relating to text messages, data,voice calls, minutes used, voice over Internet Protocol (VoIP) usage,and any other element of usage consumed by, or that impacts, the usercomputing devices to produce the data usage statistics. The data usagestatistics identify, to a granularity of time (e.g., per minute) or data(e.g., per kilobyte), how much data has been sent and/or received by themobile computing device 102 or other user computing devices and overwhich network connections 130. Other data usage statistics arecontemplated, however. For example, the data usage statistics mayfurther identify the time and day of usage, location of usage, networkconnection 130, technology usage, the subscriber identity module (SIM)card or other user identity module used for dual SIM scenarios, theinternational mobile station equipment identity (IMEI) or other deviceidentifier for multi-device scenarios, the Internet protocol (IP)address or other address of the access point used for Wi-Fi scenarios,the IP address or other address of the target computer (e.g., forwhitelist/blacklists in data usage), the application responsible for thedata transfer, etc. In some examples, the web service 108 tracks ormonitors network data consumption by the user computing devices bycompiling the data usage statistics directly (e.g., monitor networktraffic) and/or by collecting the data usage statistics from the mobilecomputing device 102 (or other user computing devices) and/or the mobileoperator 111.

For example, the web service 108 may collect, monitor, or generate firstdata usage statistics 120 from the mobile computing device 102 andsecond data usage statistics 132 from the mobile operator 111. In someembodiments, the first data usage statistics 120 represent network dataconsumed under the data usage plan by the mobile computing device 102 asdetermined and/or measured (e.g., collected and stored) by the mobilecomputing device 102. For example, the mobile computing device 102collects ongoing usage data relating to network data transfers, such asfrom device radios, drivers, and accelerometers.

In other embodiments, the first data usage statistics 120 representnetwork data consumed under the data usage plan by each of the usercomputing devices, not just the mobile computing device 102. In suchembodiments, the mobile computing device 102 receives updates of networkdata consumption by the other user computing devices sharing the samedata usage plan. The second data usage statistics 132 represent networkdata consumed under the data usage plan by the mobile computing device102 as determined and/or measured (e.g., collected and stored) by themobile operator 111. In other embodiments, the second data usagestatistics 132 represent network data consumed under the data usage planby each of the user computing devices, not just the mobile computingdevice 102. In such embodiments, the mobile operator 111 monitorsnetwork data consumption by the other user computing devices sharing thesame data usage plan. For example, the second data usage statistics 132may represent the network data collectively consumed by the mobiletelephone 404, tablet, and laptop of the user 104.

In a further example, one or more of the mobile operators 111 collectdata usage statistics corresponding to a plurality of data usage plans.In such an example, there may a plurality of sets of data usagestatistics (e.g., one set for each data usage plan or user 104).

In some embodiments, the mobile operator 111 may have more currentand/or more accurate data usage statistics 120 for one or more of theuser computing devices than the user computing devices. For example, themobile operator 111 may have more current and/or more accurate datausage statistics 120 for particular network connections 130 than theuser computing devices. The mobile operator 111 may push, or transmitupon demand, such data usage statistics 120 to the web service 108. Theweb service 108 integrates or otherwise reconciles the data from themobile operator 111 and/or the user computing devices to produce thedata usage statistics 120.

For example, if differences exist in the data usage statistics receivedfrom the mobile computing device 102 and from the mobile operator 111(e.g., the data from the mobile operator 111 may be 24-48 hours old),the web service 108 reconciles the differences to provide the user 104with the most current information. Reconciling the differences includes,for example, examining time stamps or other collection dates andfavoring, weighting, or choosing the more recently collected data. Forexample, the web service 108 may compare a timestamp associated with thefirst data usage statistics 120 and a timestamp associated with thesecond data usage statistics 132 to determine which of the data usagestatistics is more recent or up-to-date. Based on the reconciling, theweb service 108 may send a notification to one or more of the usercomputing devices. In such embodiments, upon receipt of the notificationfrom the web service 108, one or more of the user computing devices maysend a synchronization request to the web service 108. For example, theweb service 108 identifies those user computing devices that haveoutdated data usage statistics.

Upon receipt of the synchronization request from the user computingdevices, the web service 108 provides the most recent or up-to-date datausage statistics to those requesting user computing devices. Forexample, the web service 108 may provide the second data usagestatistics 132 (e.g., from the mobile operator 111) to the requestinguser computing devices.

In some embodiments, the web service 108 executes the statisticscomponent 124 to collect and analyze the data usage statistics. Thestatistics component 124, when executed by the web service 108, receivesthe first data usage statistics 120 as collected by the user computingdevice and the second data usage statistics 132 as collected by themobile operator 111. The statistics component 124 reconciles the firstdata usage statistics 120 and the second data usage statistics 132, andsends a synchronization notification to the user computing device basedon the reconciliation. For example, if the statistics component 124determines that the first data usage statistics 120 collected ormaintained by the user computing device is out-of-date, the web service108 sends the synchronization notification to the user computing device.In response to receiving the synchronization notification, the usercomputing device synchronizes the first data usage statistics 120 withthe second data usage statistics 132 (e.g., compares timestampsassociated with the first data usage statistics 120 and the second datausage statistics 132). For example, the user computing device mayreplace the first data usage statistics 120 with the second data usagestatistics 132.

The web service 108 may store the schema component 122 and thestatistics component 124 on one or more computer storage media. Further,the schema component 122 and the statistics component 124 may executeindependently of each other (e.g., not sequentially, or withoutinteraction or dependency between the two components). For example, theschema component 122 and the statistics component 124 may each beexecuted by a separate thread.

Referring next to FIG. 3, an exemplary flow chart illustrates operationof a computing device such as the mobile computing device 102 to collectand reconcile data usage statistics describing network data consumedunder the data usage plan. While the operations illustrated in FIG. 3are performed by the computing device of the user 104 in someembodiments, one or more of the operations may be performed by otherdevices, including any computing device local to, or remote from, theuser 104. For example, the operations may be performed by a proxy devicein communication with the computing device. As an example, theoperations illustrated in FIG. 3 may be performed by an operating systemexecuting on the mobile computing device 102.

At 302, the computing device collects data usage statistics (e.g., thefirst data usage statistics 120) relating to the data usage plan. Thefirst data usage statistics 120 represent network data consumption underthe data usage plan by the computing device as determined by thecomputing device. The computing device stores the collected first datausage statistics 120 in, for example, the memory area 112. At 304, thecomputing device receives data usage statistics (e.g., the second datausage statistics 132) relating to the data usage plan. The second datausage statistics 132 represent network data consumption under the datausage plan by the computing device as determined by the mobile operator111.

At 306, the computing device reconciles the collected first data usagestatistics 120 and the received second data usage statistics 132. Forexample, the computing device may compare timestamps associated with thefirst data usage statistics 120 and the second data usage statistics 132to identify the more recent, or up-to-date, measure of network dataconsumption under the data usage plan. At 308, the computing deviceupdates the first data usage statistics 120 based on the reconciliation.For example, the computing device may conclude that the first data usagestatistics 120 are more recent and hence more accurately representcurrent, cumulative network data consumption than the second data usagestatistics 132. In such an example, the computing device makes nochanges to the collected first data usage statistics 120.

As another example, the computing device may conclude that the seconddata usage statistics 132 are more recent and hence more accuratelyrepresent current, cumulative network data consumption than the firstdata usage statistics 120. In such an example, the computing device mayreplace the first data usage statistics 120 stored in the memory area112 with the second data usage statistics 132.

As described with reference to FIG. 3, the first data usage statistics120 represent network data consumed by the computing device, asmonitored by the computing device. In other embodiments, the first datausage statistics 120 may represent network data consumed by thecomputing device and the other computing devices 106 sharing the datausage plan. For example, the computing device may collect the first datausage statistics 120 by receiving at least a portion of the first datausage statistics 120 from these other computing devices 106 associatedwith the data usage plan. In such embodiments, after reconciling thedata usage statistics (e.g., updating the first data usage statistics120 with the second data usage statistics 132), the computing device maysend the updated first data usage statistics 120 to the other computingdevices 106 based on the reconciliation. Alternatively or in addition,the computing device may send a synchronization notification to theother computing devices 106 prompting those computing devices tosynchronize the data usage statistics with those from the computingdevice.

Referring next to FIG. 4, an exemplary user interface 402 on the mobiletelephone 404 illustrates configuration options for importing datadescribing the data usage plan. In the example of FIG. 4, the user 104is able to explicitly opt-in or opt-out of receiving the schema 116populated with the data usage plan. For example, the mobile telephone404 asks permission from the user 104 to retrieve the wireless plandetails to help avoid overcharges. The user 104 checks a checkbox toimport the populated schema 116. In response, the mobile telephone 404requests the populated schema 116 from the mobile operator 111 and, uponreceipt from the mobile operator 111, the mobile telephone 404 storesthe populated schema 116 in the memory area 112.

Referring next to FIG. 5, an exemplary user interface 502 illustratescompletion of synchronization of data describing the data usage plan. Inthe example of FIG. 5, the user 104 has opted-in to obtaining, from themobile operator 111, the schema 116 populated with the data usage planthat the user 104 and mobile operator 111 have agreed upon. The user 104receives confirmation that the details of the data usage plan have beendownloaded, as displayed in the user interface 502 of the mobiletelephone 404. The populated schema 116 includes details of the datausage plan, such as the start date of the billing cycle. The userinterface 502 in FIG. 5 further displays the start date of the billingcycle to the user 104. The user interface 502 also displays a messagetelling the user 104 how to check current usage and modify accountsettings.

Referring next to FIG. 6, an exemplary user interface 602 illustrates asummary of network data usage with different types of networkconnections 130. While the proportions of the user interfaces 602, 702,704, 706 illustrated in FIG. 6, FIG. 7A, FIG. 7B, FIG. 7C, and FIG. 8are shown to conform to a screen of the mobile computing device 102(e.g., the mobile telephone 404), the content displayed within the userinterfaces 602, 702, 704, 706 may be shown in any format on any of theuser computing devices.

In FIG. 6, data usage for a plurality of the network connections 130 isshown to the user 104 in the user interface 602. In particular, datausage statistics 120 attributed to each of the network connections 130is shown. For example, the amounts of data transmitted and/or receivedover a cellular network connection, a tethered network connection, aHotspot network connection, and a Wi-Fi network connection are shown.The amounts of data are represented by proportionally-sized horizontalbars.

The user interface 602 also displays the threshold values 118 associatedwith each of the network connections 130. The threshold values 118 aretaken from the data usage plan. For example, the data usage planindicates that the user 104 has a maximum of 5 gigabytes (GB) of datausage available for the cellular network connection, 2 GB of data usagefor the tethered network connection, 1 GB of data usage for the Hotspotnetwork connection, and an unlimited amount of data usage for the Wi-Finetwork connection.

The user interface 602 in FIG. 6 may also display a button or bar that,when selected by the user 104 (e.g., clicked or touched), the userinterface 602 allows the user 104 to select options or otherconfiguration settings for receiving notifications. The notificationsare sent when the amounts of data transmitted and/or received over thevarious network connections 130 reaches particular values (e.g., set bythe user 104, mobile computing device 102, mobile operator 111, or otherentity).

Referring next to FIG. 7A, an exemplary user interface 702 illustratesdata usage by the mobile computing device 102 consuming network dataunder the data usage plan having a monthly limit. While the overviews ofdata usage illustrated in FIG. 7A, FIG. 7B, and FIG. 7C indicate thatthe data usage statistics 120 shown are per application 114, the userinterfaces 702, 704, 706 may alternatively or in addition display anoverview of aggregated data usage across the applications 114 on themobile computing device 102. Further, the user interfaces 702, 704, 706may alternatively or in addition display an overview of data usage percomputing device of the user 104 or aggregated across a plurality of thecomputing devices of the user 104. For example, the different statisticsmay be shown in different tabs or tiles in the user interfaces 702, 704,706. In an example involving a family or shared data plan, thestatistics for each plan member may be shown in separate tiles.

In FIG. 7A, the data usage statistics 120 include the amount of networkdata remaining for use (e.g., the remainder of the monthly limitspecified by the data usage plan), the amount of network data usedduring the current billing period, and the quantity of time (e.g., days)remaining within the current billing period. The data usage statistics120 also indicate a breakout of the data usage, such as the amount ofdata consumed under a cellular network connection versus the amount ofdata consumed under a Wi-Fi network connection.

Referring next to FIG. 7B, an exemplary user interface 704 illustratesdata usage by the mobile computing device 102 consuming network dataunder a pay-as-you-go data usage plan. In FIG. 7B, the data usagestatistics 120 include the amount of network data consumption remainingfor use (e.g., the remainder of the pay-as-you-go amount specified bythe data usage plan), the amount of network data consumed recently(e.g., within the last 30 days), and the quantity of time (e.g., days)remaining. For example, the remaining cellular data consumption expiresin 16 days. The data usage statistics 120 also indicate a breakout ofthe data usage, such as the amount of data consumed under a cellularnetwork connection versus the amount of data consumed under a Wi-Finetwork connection.

Referring next to FIG. 7C, an exemplary user interface 706 illustratesdata usage by the mobile computing device 102 consuming network dataunder the data usage plan with unlimited data usage. In FIG. 7C, thedata usage statistics 120 include the amount of network data consumedrecently (e.g., within the last 30 days). The data usage statistics 120also indicate a breakout of the data usage, such as the amount of dataconsumed under a cellular network connection versus the amount of dataconsumed under a Wi-Fi network connection. The data usage statistics 120also indicate a total amount of usage by the mobile computing device102.

Referring next to FIG. 8, an exemplary block diagram illustrates themobile computing device 102 as the mobile telephone 404 having a tilefor displaying the data usage statistics 120 to the user 104. The mobiletelephone 404 displays a plurality of tiles (e.g., active tiles) thatmay be updated with the data usage statistics 120. In some embodiments,tiles represent tile user interface elements. In the example of FIG. 8,the mobile telephone 404 indicates that 78% of the allotment for textmessages has been consumed, while 55% of the allotment for data usagehas been consumed.

Additional Examples

In an example scenario, the user 104 has several user computing devicesassociated with the same data usage plan. For example, the user 104 hasa smartphone, a tablet, and a basic cellular telephone. In this example,the user 104 also has two subscriber identity module (SIM) cards orother user identity modules (e.g., two universal integrated circuitcards), each associated with a different data usage plan. Over time, theuser 104 moves the SIM cards among the smartphone, tablet, and cellulartelephone. After the user 104 installs one of the SIM cards in one ofthe devices, aspects of the disclosure execute on that device to detectthe new SIM card and to communicate with the mobile operator 111associated with the SIM card to obtain the schema 116 populated with thedata usage plan associated with the SIM card. The user 104 is then ableto view details of the data usage plan associated with that SIM card,such as the allotments per network connection 130 and remaining dataconsumption for the current billing cycle.

In another example scenario, the computing device may share thepopulated schema 116, or portions thereof, with other devices upondemand or request. For example, the user 104 may tether the computingdevice to a friend's computing device (e.g., configure the computingdevice to be a wireless access point). The friend's computing devicecommunicates with the user's computing device to obtain the schema 116populated with the data usage plan. The friend is then able to view anamount of data consumption remaining under the data usage planassociated with the user 104 thus enabling the friend to decide whether,and how much, network data may be consumed.

At least a portion of the functionality of the various elements in FIG.1 may be performed by other elements in FIG. 1, or an entity (e.g.,processor, web service, server, application program, computing device,etc.) not shown in FIG. 1.

In some embodiments, the operations illustrated in FIG. 2 and FIG. 3 maybe implemented as software instructions encoded on a computer readablemedium, in hardware programmed or designed to perform the operations, orboth. For example, aspects of the disclosure may be implemented as asystem on a chip or other circuitry including a plurality ofinterconnected, electrically conductive elements.

The term “roaming” as used herein refers, in some embodiments, toconnectivity provided outside a subscriber's home zone that may besubject to additional tariffs, fees, or constraints. Roaming service mayor may not be provided by the same mobile operator 111. The term“tethered” as used herein refers, in some embodiments, to situationswhere one device acts as an access point for another device for networkaccess. A tethered connection may occur over a wired connection or awireless connection. The term “Wi-Fi” as used herein refers, in someembodiments, to a wireless local area network using high frequency radiosignals for the transmission of data. The term “BLUETOOTH” as usedherein refers, in some embodiments, to a wireless technology standardfor exchanging data over short distances using short wavelength radiotransmission. The term “cellular” as used herein refers, in someembodiments, to a wireless communication system using short-range radiostations that, when joined together, enable the transmission of dataover a wide geographic area. The term “NFC” as used herein refers, insome embodiments, to a short-range high frequency wireless communicationtechnology for the exchange of data over short distances.

Embodiments have been described with reference to data monitored and/orcollected from users 104. In some embodiments, notice may be provided tothe users 104 of the collection of the data (e.g., via a dialog box orpreference setting) and users 104 are given the opportunity to give ordeny consent for the monitoring and/or collection. The consent may takethe form of opt-in consent or opt-out consent.

Exemplary Operating Environment

Exemplary computer readable media include flash memory drives, digitalversatile discs (DVDs), compact discs (CDs), floppy disks, and tapecassettes. By way of example and not limitation, computer readable mediacomprise computer storage media and communication media. Computerstorage media include volatile and nonvolatile, removable andnon-removable media implemented in any method or technology for storageof information such as computer readable instructions, data structures,program modules or other data. Computer storage media are tangible andare mutually exclusive to communication media. In some embodiments,computer storage media are implemented in hardware. Exemplary computerstorage media include hard disks, flash drives, and other solid-statememory. In contrast, communication media typically embody computerreadable instructions, data structures, program modules, or other datain a modulated data signal such as a carrier wave or other transportmechanism and include any information delivery media.

Although described in connection with an exemplary computing systemenvironment, embodiments of the disclosure are capable of implementationwith numerous other general purpose or special purpose computing systemenvironments, configurations, or devices.

Examples of well-known computing systems, environments, and/orconfigurations that may be suitable for use with aspects of theinvention include, but are not limited to, mobile computing devices,personal computers, server computers, hand-held or laptop devices,multiprocessor systems, gaming consoles, microprocessor-based systems,set top boxes, programmable consumer electronics, mobile telephones,network PCs, minicomputers, mainframe computers, distributed computingenvironments that include any of the above systems or devices, and thelike. Such systems or devices may accept input from the user 104 in anyway, including from input devices such as a keyboard or pointing device,via gesture input, and/or via voice input.

Embodiments of the invention may be described in the general context ofcomputer-executable instructions, such as program modules, executed byone or more computers or other devices. The computer-executableinstructions may be organized into one or more computer-executablecomponents or modules. Generally, program modules include, but are notlimited to, routines, programs, objects, components, and data structuresthat perform particular tasks or implement particular abstract datatypes. Aspects of the invention may be implemented with any number andorganization of such components or modules. For example, aspects of theinvention are not limited to the specific computer-executableinstructions or the specific components or modules illustrated in thefigures and described herein. Other embodiments of the invention mayinclude different computer-executable instructions or components havingmore or less functionality than illustrated and described herein.

Aspects of the invention transform a general-purpose computer into aspecial-purpose computing device when configured to execute theinstructions described herein.

The embodiments illustrated and described herein as well as embodimentsnot specifically described herein but within the scope of aspects of theinvention constitute exemplary means for collecting and reconciling thefirst data usage statistics 120 (e.g., as collected by the usercomputing devices) and the second data usage statistics 132 (e.g., ascollected by the mobile operators 111), and exemplary means forsynchronizing the first data usage statistics 120 with the second datausage statistics 132.

The order of execution or performance of the operations in embodimentsof the invention illustrated and described herein is not essential,unless otherwise specified. That is, the operations may be performed inany order, unless otherwise specified, and embodiments of the inventionmay include additional or fewer operations than those disclosed herein.For example, it is contemplated that executing or performing aparticular operation before, contemporaneously with, or after anotheroperation is within the scope of aspects of the invention.

When introducing elements of aspects of the invention or the embodimentsthereof, the articles “a,” “an,” “the,” and “said” are intended to meanthat there are one or more of the elements. The terms “comprising,”“including,” and “having” are intended to be inclusive and mean thatthere may be additional elements other than the listed elements. Theterm “exemplary” is intended to mean “an example of” The phrase “one ormore of the following: A, B, and C” means “at least one of A and/or atleast one of B and/or at least one of C.”

Having described aspects of the invention in detail, it will be apparentthat modifications and variations are possible without departing fromthe scope of aspects of the invention as defined in the appended claims.As various changes could be made in the above constructions, products,and methods without departing from the scope of aspects of theinvention, it is intended that all matter contained in the abovedescription and shown in the accompanying drawings shall be interpretedas illustrative and not in a limiting sense.

APPENDIX A

Listed below are exemplary schema portions that are operable in aspectsof the disclosure. While written in extensible markup language (XML)format, the schema may be implemented in other formats.

<?xml version=“1.0” encoding=“UTF-8”?> <xs:schema xmlns:xs=“Base/v1”elementFormDefault=“qualified” targetNamespace=“CarrierControl/Base/v1”>  <!-- Basic types -->  <xs:simpleType name=“NameType”>  <xs:restriction base=“xs:normalizedString”>    <xs:minLengthvalue=“1”/>    <xs:maxLength value=“255”/>    <xs:whiteSpacevalue=“collapse”/>   </xs:restriction> </xs:simpleType>  <xs:simpleTypename=“Priority”>   <xs:restriction base=“xs:nonNegativeInteger”>   <xs:maxExclusive value=“10”/>   </xs:restriction>  </xs:simpleType> <xs:simpleType name=“GUID”>   <xs:annotation>    <xs:documentationxml:lang=“en”> The representation of a GUID, generally the id of anelement. </xs:documentation>   </xs:annotation>   <xs:restrictionbase=“xs:token”>    <xs:patternvalue=“\{[a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{12}\}”/>   </xs:restriction>  </xs:simpleType> <xs:simpleType name=“SubscriberType”>   <xs:restrictionbase=“xs:token”>    <xs:maxLength value=“20”/>    <xs:patternvalue=“\w+”/>   </xs:restriction>  </xs:simpleType>  <xs:complexTypename=“CertificateDetails”>   <xs:annotation>    <xs:documentation> Usedto identify a certificate or set of certificates. SubjectName iscompared against the DN provided as the certificate's Subject field, oragainst any Name provided in the SubjectAlternativeName extentions oftype DirectoryName. IssuerName is compared against the DN provided asthe certificate's Issuer field, or against any Name provided in theIssuerAlternativeName extentions of type DirectoryName.</xs:documentation>   </xs:annotation>   <xs:sequence>    <xs:elementname=“SubjectName” type=“xs:string”/>    <xs:element name=“IssuerName”type=“xs:string”/>   </xs:sequence>  </xs:complexType>   <!-- Aliasdefinitions -->  <xs:element name=“AliasList”>   <xs:complexType>   <xs:sequence>     <xs:element maxOccurs=“unbounded”ref=“AliasDefinition”/>    </xs:sequence>   </xs:complexType> </xs:element>  <xs:complexType name=“AliasDefinitionBaseType”>  <xs:attribute name=“Name” type=“xs:string”/>  </xs:complexType> <xs:element name=“AliasDefinition” type=“AliasDefinitionBaseType”abstract=“true”/>   <!-- Locations -->  <xs:simpleTypename=“ProviderNameType”>   <xs:restriction base=“xs:normalizedString”>   <xs:minLength value=“1”/>    <xs:maxLength value=“20”/>   <xs:whiteSpace value=“collapse”/>   </xs:restriction> </xs:simpleType>  <xs:simpleType name=“ProviderIdType”>  <xs:restriction base=“xs:token”>    <xs:pattern value=“\d{1,6}”/>  </xs:restriction>  </xs:simpleType>  <xs:complexTypename=“ProviderType”>   <xs:sequence>    <xs:element name=“ProviderID”type=“ProviderIdType”/>    <xs:element name=“ProviderName”type=“ProviderNameType”/>   </xs:sequence>  </xs:complexType> <xs:complexType name=“LocationType”>   <xs:choicemaxOccurs=“unbounded”>    <xs:element name=“Provider”type=“ProviderType”/>    <xs:element name=“LocationAlias”type=“xs:string”/>   </xs:choice>   <xs:attribute name=“negate”type=“xs:boolean” default=“false”/>  </xs:complexType>  <xs:elementname=“LocationAliasDefinition” type=“LocationAliasDefinitionType”substitutionGroup=“AliasDefinition”/>  <xs:complexTypename=“LocationAliasDefinitionType”>   <xs:complexContent>   <xs:extension base=“AliasDefinitionBaseType”>     <xs:sequence>     <xs:element name=“Location” type=“LocationType”/>    </xs:sequence>    </xs:extension>   </xs:complexContent> </xs:complexType>   <!-- Times -->  <xs:complexType name=“TimeType”>  <xs:choice maxOccurs=“unbounded”>    <xs:element name=“TimePeriod”type=“TimePeriod”/>    <xs:element name=“RecurringTimePeriod”type=“RecurringTimePeriod”/>    <xs:element name=“TimeAlias”type=“xs:string”/>   </xs:choice>   <xs:attribute name=“negate”type=“xs:boolean” default=“false”/>  </xs:complexType>  <xs:elementname=“TimeAliasDefinition” type=“TimeAliasDefinitionType”substitutionGroup=“AliasDefinition”/>  <xs:complexTypename=“TimeAliasDefinitionType”>   <xs:complexContent>    <xs:extensionbase=“AliasDefinitionBaseType”>     <xs:sequence>      <xs:elementname=“Time” type=“TimeType” maxOccurs=“unbounded”/>     </xs:sequence>   </xs:extension>   </xs:complexContent>  </xs:complexType> <xs:simpleType name=“TimeOfWeek”>   <xs:annotation>   <xs:documentation> Defines a time as an offset from the midnightpreceding 12:00:01 AM Sunday (P0D) to the midnight following 11:59:59 PMSaturday (P7D). </xs:documentation>   </xs:annotation>   <xs:restrictionbase=“xs:duration”>    <xs:minInclusive value=“P0D”/>   <xs:maxInclusive value=“P7D”/>   </xs:restriction>  </xs:simpleType> <xs:complexType name=“RecurringTimePeriod”>   <xs:annotation>   <xs:documentation> Defines a period of time within the week as astart/end TimeOfWeek. If EndTime is less than StartTime, the period isinterpreted as crossing Saturday night. </xs:documentation>  </xs:annotation>   <xs:attribute name=“StartTime” type=“TimeOfWeek”use=“required”/>   <xs:attribute name=“EndTime” type=“TimeOfWeek”use=“required”/>  </xs:complexType>  <xs:complexType name=“TimePeriod”>  <xs:annotation>    <xs:documentation> Defines a period of time as astart/end date and time. </xs:documentation>   </xs:annotation>  <xs:attribute name=“StartTime” type=“xs:dateTime” use=“required”/>  <xs:attribute name=“EndTime” type=“xs:dateTime” use=“required”/> </xs:complexType> </xs:schema> <?xml version=“1.0” encoding=“UTF-8”?><xs:schema xmlns:base=“Base/v1” elementFormDefault=“qualified”targetNamespace=“ CarrierControl/Plans/v1”>  <xs:importschemaLocation=“Alias.xsd”   namespace=“CarrierControl/Base/v1”/>   <!--Plan Definition -->  <xs:complexType name=“BillingCycleType”>  <xs:attribute name=“StartDate” use=“required” type=“xs:dateTime”/>  <xs:attribute name=“Duration” use=“required”>    <xs:simpleType>    <xs:restriction base=“xs:duration”>      <xs:minExclusivevalue=“PT0S”/>     </xs:restriction>    </xs:simpleType>  </xs:attribute>   <xs:attribute name=“Resets” type=“xs:boolean”default=“true”/>  </xs:complexType>  <xs:simpleTypename=“CostStyleType”>   <xs:annotation>    <xs:documentation> CostTypeexpresses the incremental cost of a plan: - Unrestricted: There is noincremental cost for consumption on this plan - Fixed: Consumption goesagainst a quota which the user has purchased / agreed to purchase -Variable: The user will be billed for incremental usage on this plan</xs:documentation>   </xs:annotation>   <xs:restrictionbase=“xs:string”>    <xs:enumeration value=“Unrestricted”/>   <xs:enumeration value=“Fixed”/>    <xs:enumeration value=“Variable”/>  </xs:restriction>  </xs:simpleType>  <xs:element name=“Plan”>  <xs:complexType>    <xs:sequence>     <xs:element minOccurs=“0”ref=“Description”/>     <xs:element minOccurs=“0” ref=“Usage”/>   </xs:sequence>    <xs:attribute name=“Name” use=“required”type=“xs:string”/>   </xs:complexType>  </xs:element>  <xs:elementname=“Description” type=“DescriptionBaseType” abstract=“true”/> <xs:complexType name=“DescriptionBaseType”>  <xs:sequence>   <xs:element name=“BillingCycle” type=“BillingCycleType”minOccurs=“0”/>    <xs:element name=“Conditions” minOccurs=“0”>    <xs:complexType>      <xs:all>       <xs:element name=“Location”type=“base:LocationType” minOccurs=“0”/>       <xs:element name=“Time”type=“base:TimeType” minOccurs=“0”/>       <xs:element name=“Direction”default=“inout” minOccurs=“0”>        <xs:simpleType>        <xs:restriction base=“xs:token”>          <xs:enumerationvalue=“in”/>          <xs:enumeration value=“out”/>         <xs:enumeration value=“inout”/>         </xs:restriction>       </xs:simpleType>       </xs:element>       <xs:elementname=“Destination” minOccurs=“0”>        <xs:complexType>        <xs:annotation>          <xs:documentation> PhoneNumber onlyapplies to SMS/Voice plans; HostName only applies to data plans</xs:documentation>         </xs:annotation>         <xs:sequence>         <xs:element name=“PhoneNumber” minOccurs=“0”>          <xs:simpleType>            <xs:restriction base=“xs:string”>            <xs:pattern value=“(\+)?\d+”/>            </xs:restriction>          </xs:simpleType>          </xs:element>          <xs:elementname=“HostName” minOccurs=“0”>           <xs:simpleType>           <xs:restriction base=“xs:anyURI”/>           </xs:simpleType>         </xs:element>         </xs:sequence>        </xs:complexType>      </xs:element>       <xs:element name=“LimitedUsage” minOccurs=“0”>       <xs:annotation>         <xs:documentation> For Fixed plans,provides details on the user's quota: - Limit: The amount of the quota(in minutes for Voice plans, megabytes for Data plans, and messages forSMS plans) - SharedPlan: Another plan name whose quota is also consumedby usage on this plan - FallbackPlan: Another plan name whoseconsumption begins when this quota is exhausted. If a Fallback Plan isnot provided, the current plan goes into an Overage state.</xs:documentation>        </xs:annotation>        <xs:complexType>        <xs:attribute name=“Limit” use=“required”type=“xs:nonNegativeInteger”/>         <xs:attribute name=“SharedPlan”type=“xs:string”/>         <xs:attribute name=“FallbackPlan”type=“xs:string”/>        </xs:complexType>       </xs:element>     </xs:all>     </xs:complexType>    </xs:element>   </xs:sequence>  <xs:attribute name=“CostStyle” use=“required” type=“CostStyleType”/> </xs:complexType>  <xs:complexType name=“DataPlanDescriptionType”>  <xs:complexContent>    <xs:extension base=“DescriptionBaseType”>    <xs:sequence>      <xs:element name=“BandwidthInKbps”type=“xs:nonNegativeInteger” minOccurs=“0”/>      <xs:elementname=“MaxDownloadFileSizeInMegabytes” type=“xs:positiveInteger”default=“25” minOccurs=“0”/>      <xs:elementname=“SecurityUpdatesExempt” type=“xs:boolean” default=“false”minOccurs=“0”/>     </xs:sequence>    </xs:extension>  </xs:complexContent>  </xs:complexType>  <xs:elementname=“DataPlanDescription” type=“DataPlanDescriptionType”substitutionGroup=“Description”/>  <xs:complexTypename=“SmsPlanDescriptionType”>   <xs:complexContent>    <xs:extensionbase=“DescriptionBaseType”/>   </xs:complexContent>  </xs:complexType> <xs:element name=“SmsPlanDescription” type=“SmsPlanDescriptionType”substitutionGroup=“Description”/>  <xs:complexTypename=“VoicePlanDescriptionType”>   <xs:complexContent>    <xs:extensionbase=“DescriptionBaseType”/>   </xs:complexContent>  </xs:complexType> <xs:element name=“VoicePlanDescription” type=“VoicePlanDescriptionType”substitutionGroup=“Description”/>  <xs:element name=“Usage”type=“PlanUsageType”/>  <xs:complexType name=“PlanUsageType”>  <xs:attribute name=“PlanName” use=“required” type=“xs:string”/>  <xs:attribute name=“OverLimit” type=“xs:boolean”/>   <xs:attributename=“Congested” type=“xs:boolean”/>   <xs:attribute name=“CurrentUsage”use=“required” type=“xs:nonNegativeInteger”/>   <xs:attributename=“UsageTimestamp” use=“required” type=“xs:dateTime”/> </xs:complexType> </xs:schema>

What is claimed is:
 1. A system comprising: a memory area associatedwith a mobile computing device, said memory area storing first datausage statistics, the first data usage statistics representing networkdata consumed by the mobile computing device under a data usage plan;and a processor programmed to: collect the first data usage statisticsrelating to the data usage plan and store the collected first data usagestatistics in the memory area; receive second data usage statisticsrelating to the data usage plan as collected by a mobile operator;reconcile the collected first data usage statistics and the receivedsecond data usage statistics; and update the first data usage statisticsstored in the memory area based on the reconciliation.
 2. The system ofclaim 1, wherein the processor is programmed to collect the first datausage statistics by receiving at least a portion of the first data usagestatistics from other computing devices associated with the data usageplan.
 3. The system of claim 2, wherein the processor is furtherprogrammed to send the updated first data usage statistics to the othercomputing devices based on the reconciliation.
 4. The system of claim 2,wherein the processor is further programmed to send a synchronizationnotification to the other computing devices based on the reconciliation,wherein the other computing devices obtain the updated first datastatistics in response to the synchronization notification.
 5. Thesystem of claim 1, further comprising means for collecting andreconciling the first data usage statistics and the second data usagestatistics.
 6. The system of claim 1, further comprising means forsynchronizing the first data usage statistics with the second data usagestatistics.
 7. A method comprising: receiving, from at least one mobileoperator, a schema populated with data describing a data usage planassociated with one or more user computing devices; distributing thereceived, populated schema to the user computing devices; subsequentlyreceiving, from the mobile operator, an updated portion of the schema,the updated portion of the schema corresponding to an updated portion ofthe data usage plan; and distributing only the received, updated portionof the schema to the user computing devices.
 8. The method of claim 7,further comprising: collecting first data usage statistics relating tothe data usage plan from the user computing devices; and collectingsecond data usage statistics relating to the data usage plan from themobile operator.
 9. The method of claim 8, further comprisingreconciling the received first data usage statistics and the receivedsecond data usage statistics.
 10. The method of claim 9, whereinreconciling the received first data usage statistics and the receivedsecond data usage statistics comprises comparing a timestamp associatedwith the received first data usage statistics and a timestamp associatedwith the received second data usage statistics.
 11. The method of claim9, further comprising sending a synchronization notification to the usercomputing devices based on said reconciling.
 12. The method of claim 7,wherein the schema comprises an extensible markup language schema. 13.The method of claim 7, wherein the data usage plan describes thresholdvalues associated with network connections of the user computingdevices.
 14. The method of claim 13, wherein the threshold valuescorrespond to maximum network data allotted under the data usage planfor the network connections.
 15. The method of claim 13, wherein each ofthe threshold values correspond to one of a plurality of fields in theschema.
 16. The method of claim 16, wherein each of the plurality offields comprises one or more of the following: peak times, off-peaktimes, peak time data consumption quota, off-peak time data consumptionquota, peak time data consumption remaining, off-peak time dataconsumption remaining, a roaming rate, a mobile operator name, a billingcycle type, and a network connection type.
 17. One or more computerstorage media embodying computer-executable components, said componentscomprising: a schema component that when executed causes at least oneprocessor to: receive, from at least one mobile operator, a schemapopulated with data describing a data usage plan associated with atleast one user computing device, distribute the received, populatedschema to the user computing device, subsequently receive, from themobile operator, an updated portion of the schema, the updated portionof the schema corresponding to an updated portion of the data usageplan, and distribute only the received, updated portion of the schema tothe user computing device; and a statistics component that when executedcauses at least one processor to: receive first data usage statisticsrelating to the data usage plan as collected by the user computingdevice, receive second data usage statistics relating to the data usageplan as collected by the mobile operator, reconcile the received firstdata usage statistics and the received second data usage statistics, andsend a synchronization notification to the user computing device basedon said reconciling.
 18. The computer storage media of claim 17, whereinthe statistics component reconciles the received first data usagestatistics and the received second data usage statistics by comparing atimestamp associated with the received first data usage statistics and atimestamp associated with the received second data usage statistics. 19.The computer storage media of claim 17, wherein the first data usagestatistics and the second data usage statistics received by thestatistics component represent network data consumed by the usercomputing device under the data usage plan.
 20. The computer storagemedia of claim 17, wherein the schema component and the statisticscomponent execute independently of each other.